REXX & SOM fixes for OS/2 Warp Version 3
                         Sept. 29, 1996

REXXSOM.ZIP contains:

 8-15-96   1:11p    261871   REXX.DLL
10-31-94   7:31p     33415   REXXAPI.DLL
10-31-94   7:31p      1484   REXXINIT.DLL
10-31-94   7:32p     30315   REXXUTIL.DLL
 7-30-96   9:23p    133593   SOM.DLL

It can be downloaded via anonymous FTP from ftp.cfsrexx.com and
is located in /pub/rexxsom.zip. It can also be accessed with Web
browser at http://www.cfsrexx.com on the REXX-related files page. 

The new DLLs (REXX.DLL & SOM.DLL) fix all of the known problems
with VX-REXX on OS/2 Warp Version 3 including:

1)   SYS3175 when exiting a VRXEDIT session as well as other
     SYS3175 traps in a VX-REXX environment.

2)   Spin button events not being passed back to a VX-REXX
     program.

3)   The VRCREATE() function hanging for no discernable reason.

The older REXX-related DLLs are included in the event that you
have applied FixPaks which installed incompatible REXX DLLs and
the group of DLLs included here have been tested together.

The two new DLLs (REXX.DLL & SOM.DLL) will be included in IBM's
FixPaks beginning with FixPak 25, though there is no assurance
that FixPak 25 will be a public FixPak. These same fixes are
included in the Warp Version 4 (a.k.a. Merlin) GA code.

The enclosed DLLs will have to be installed from a command line
without the Workplace Shell being active. To accomplish this, re-IPL (re-boot) to an OS/2 command line. You get there by <Alt-F1>
while the white rectangle is displayed on the top left corner of
your screen and selecting <C> - command line. You can then enter
the following commands (or create a procedural .CMD file - not
REXX):

     cd \os2\dll
     rename rexx*.dll rexx*.bak
     copy ?\rexx*.dll
     rename som.dll som.bak
     copy ?\som.dll

where ? is the path where you unzipped REXXSOM.ZIP.

Dick Goran
dgoran@cfsrexx.com
http://www.cfsrexx.com

P.S. I have been running with these DLLs installed since mid-August with no negative effects. However, as always, be sure
     you have adequate backup of your original DLLs before
     activating these.